Downstream Message Push Overview

Downstream message push (DMP) feature adds the ability to push appropriate notifications to a downstream application on completion of activity processing, before data is committed to the database. A user can configure this feature in Palette without any need for external files using the PushNotifications ABR and DownstreamMessagePushDefinition system rule. The DownstreamMessagePushDefinition rules define a message structure and the PushNotifications rule is configured to deliver messages to the downstream applications through the JMS/SOAP protocols. This functionality can be enabled by the configuration provided in these business rules.

OIPA supports DMP, when activities are run manually, through DI, Webservices and Cycle.

Important: Cycle properties file should contain the property downstream.service.event.mode enabled in order to support DMP for activities that run through Cycle.

The DownstreamMessagePushDefinition rule can be overridden at Primary company level and Plan level. PushNotifications ABR can be overridden at Plan Activity, Policy Activity, Client Activity, Company Activity and Customer Activity.

Supported Transaction for DMP

PushNotifications for DMP is supported for the following transactions types:

  • Client-Financial-Reversible-Non-Reversing

  • Client-Document

  • Client-Financial-Nonreversible-Nonreversing

  • Client-Document-Nonreversible-Nonreversing

  • Client-Financial

  • Policy-Financial

  • Policy-Document Policy-Illustration

  • Policy-Financial-Reversible-Nonreversing

  • Policy-Document-Reversible-Nonreversing

  • Policy-Financial-Nonreversible-Nonreversing

  • Policy-Document-Nonreversible-Nonreversing

  • Policy-IssueDocument

Unsupported Transactions for DMP

PushNotifications for DMP is not supported for the following transactions:

  • Client-GCQuote

  • Client-ScreenUpdate

  • Intake-File

  • Intake-Record

  • Plan-Document

  • Plan-Document-Nonreversible-Nonreversing

  • Plan-Financial

  • Plan-Financial-Nonreversible-Nonreversing

Message Templates

Downstream message templates can be constructed using custom configuration for push notifications. PushNotifications Business Rule can be configured to define an action that needs to be taken when a message push fails or an activity processing fails.

Codes for Downstream Message Push (AsCode)

Downstream Message Push feature uses a system code AsCodeOutboundSourceType to map the SourceType with the AcOutboundEvent table of Admin Console.

  • Code Name: AsCodeOutboundSourceType
  • Code Value: ACT
  • Short Description: Activity
  • Long Description: Source type Activity

DB table AcOutboundEvent

A database table AcOutboundEvent in Admin Console is used to capture the logs for all the events, messages generated, and response received into the table. Every step of the Downstream message life cycle sends a notification to this database table.

Important: The Admin Console must be up and running, to track these outgoing messages.